That's pretty cool, definitely helps when people download projects or templates that require this to be installed.

The feature sounds good. I'm not fully sold on the name, as it starts with --export but it actually performs a setup/install. Maybe --setup-android-build-template would be better? The description of the option should also clarify that it has to be used together with one of the actual --export-* options, otherwise it's a no-op from what I can tell (didn't test, but from reading the code).

Architecturally though, I'm not fully satisfied with the implementation, as it breaks platform encapsulation, adding Android specific code in main.cpp and editor_node.cpp, notably in the generic EditorNode::export_preset. Other platforms in the future may also need pre-export steps to be performed and it would be better to have a system for this so that any export preset can specify what steps should be ensured before an export, either automatically or optionally with a command line argument.

That being said, the issue pre-exists this PR, since install_android_template() is a method of the generic ExportTemplateManager, and we expose a dedicated option in the editor to install the Android template. So that's not something that needs to be fixed in this PR, but I do think we need to rethink this stuff in the future.

In the previous version I used the name --export-android-build-template because I wanted an implicit association with the other export options (--export-release, --export-debug, --export-pack), but you're right - it is better to have the dependency on performing an export explicitly stated rather than trying to use implicit name-association.

How's about --install-android-build-template as that's the exact text of the UI/Menu option, so no new terminology (Export / Setup) is introduced. The help now shows:

  --install-android-build-template  Install the android build template. Used in conjunction with --export-release or --export-debug.

Thanks!